System and method for railroad tie management

ABSTRACT

A Railroad Tie Management System is disclosed that can provide an efficient and organized method of inspecting and auditing ties in a rail system. Tie mark files can be retrieved by a client from a server or database in operable communication with the client, and upon instantiation of an inspection process governed by the system, an inspection information table and tie grid can be generated. The tie grid can operable to receive commands from a user, and the inspection information table is operable to automatically increment and decrement fields contained within in response to changes within the tie grid. The tie grid can also be configured to incorporate data from tie scans and serve the data to the client in a useful and user-friendly manner.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a Continuation Application of U.S. patentapplication Ser. No. 17/124,824, filed on Dec. 17, 2020, entitled“SYSTEM AND METHOD FOR RAILROAD TIE MANAGEMENT,” the contents of whichare incorporated herein in their entireties for all purposes.

TECHNICAL FIELD

The present disclosure generally relates to the management of railroadties disposed throughout a railroad system infrastructure.

BACKGROUND

Rail transport systems traverse entire continents to enable thetransport and delivery of passengers and goods throughout the world. Aquintessential component of railroad infrastructure is the track—laidover a myriad of geographies and terrains, railroad tracks are designedto withstand the worst of the elements and facilitate disbursement oflocomotives throughout the railroad system. Because of this constantexposure of the tracks to hazardous conditions, railroad companies mustbe vigilant in maintaining track integrity; if a section of track iscompromised and the damage or obstruction is not quickly addressed, theconsequences can be catastrophic.

There are millions of ties in any given railroad infrastructure, andtheir integrity must be maintained at all times to ensure the safetravel of freight cars on the tracks. To ensure tie integrity, railroadsystems utilize specialized equipment to inspect the ties and determinethe overall condition of the ties. For example, Aurora® scanningtechnology, disposed on trucks capable of traveling on rails, are usedto gather data regarding the exterior (i.e. surface conditions such ascracks, breaks, etc.)) and interior (i.e. density changes due to rot,disintegration, etc.) of the ties. For management purposes, railroadtracks are often broken up into divisions, subdivisions, line segments,etc., and locations on the track are often referred to by milepostmarkers, much like mile markers on a highway. Additionally, railroadties are often labeled by individual numbers that correspond to thespecific area they are in. For example, a railroad tie can be number5423 in a specific subdivision, and railroad personnel can narrow downthe search for this specific tie by looking in between the mileposts thetie is known to lay between.

While such organizational methods and specialized equipment are usefulin gathering and managing information about railroad ties, railroadpersonnel are still needed to further inspect ties and make the finaldecision as to whether a tie needs to be replaced. However, themonitoring and inspecting of millions of ties in a railroad system isextremely difficult to manage and organize.

SUMMARY

The present disclosure achieves technical advantages as a System andMethod for Railroad Tie Management that can provide an organizationaland adaptive infrastructure configured to facilitate railroad tieinspection. The system enables individual clients to have segmented,assignable access to the entire tie mark file system and only access tiemark files as needed or assigned. The system can provide a customizableuser interface to identify, characterize, and process informationrelated to railroad ties. Additionally, the railroad tie managementsystem can generate an inspection information table and a tie grid tofacilitate tie inspection management.

The present disclosure solves the technological problem of organizingand managing the multitude of ties in any given railroad infrastructure.For example, the railroad tie management system can document informationfor railroad ties by milepost, track code, and line segment, identifyand alert a user as to those ties that are scheduled to be replaced, andalgorithmically determine from tie scans a tie grade for each tie forprocessing in accordance with a railroad tie replacement schedule. Thesystem is operable to receive commands relevant to tie inspection on aper-tie basis and ties marked for replacement can be easily unmarked.The system can integrate data generated by various scanning technologiesand can provide real-time (sub millisecond) data to inspectors that canbe directly and immediately leveraged during the inspection process.This will save the inspectors time and help ensure the accuracy of theinformation being entered into the system.

Track ties are a key component of railroad track infrastructure. Thewheels of the locomotive travel along two parallel railroad track rails.Railroad ties can be slats that are laid between and underneath therails of a track. The rails can be secured substantially perpendicularlyto the ends of the ties. The ties can maintain the three-dimensionalcoordinates of the track—“gauge,” “line,” and “surface.” The track gaugecan refer to the distance between the two railroad track rails, thetrack gage must be preserved for the proper operation of the freightcars on the rails. The line of the track can refer to the planarposition of the rails. For example, the rails can be straight orcalculatedly curved around obstacles, such as a mountainside. The“surface” of the track can be the vertical displacement of the rails,such as when the rails traverse hilly areas. Ties can be made of manydifferent materials, including wood, concrete, metal, plastic, or anyother material suitable to maintain the predetermined gauge, line, andsurface of the rails.

The railroad tie management system can include a networked server inoperable communication with a database, wherein networked computingdevices can access the database via the server to retrieve tie markfiles for inspection process instantiation. In another exemplaryembodiment, the railroad tie management system comprises control logicoperable to receive user commands to edit a tie mark file accordingly.In another embodiment, a railroad tie management system includes amultitude of subsystems through which tie management and inspection canbe achieved, such as a dashboard subsystem, a tie mark retrievalsubsystem, a tie audit subsystem, and a settings subsystem.

In one exemplary embodiment, the present disclosure can include a methodfor managing ties in a railroad system, the method comprising the stepsof: creating and storing in memory a plurality of tie mark files;receiving a request via an encrypted network for a first tie mark filehaving railroad tie data; serving the first tie mark file to the clientvia the encrypted network; and instantiating, via a processor, aninspection process to generate an inspection information table and a tiegrid, using the railroad tie data, wherein the tie grid includesmetadata related to a first tie. The method further comprising the stepof sorting the first tie mark file according to predeterminedcategories. The method further comprising the step of selecting a firsttie mark file. Wherein the first tie mark file includes the ties for apredetermine section of a railroad track. The method further comprisingreceiving an entry selecting the first tie and generating a graphicemphasizing the selection via the processor. The method furthercomprising generating an indication if the first tie is marked forreplacement. The method further comprising changing the first tiemetadata, via the processor, if a FLIP command is received. The methodfurther comprising instantiating an image capture function of the clientand storing a captured image in the first tie metadata. The methodfurther comprising instantiating, via the processor, a user input fieldand storing input data in the first tie metadata. The method furthercomprising determining railroad track characteristics and displaying therailroad track characteristics in the tie grid.

In another exemplary embodiment, the present disclosure can includerailroad tie management system, including: a data storage devicecomprising a first database with a plurality of tie mark files; and anetworked computer processor operably coupled to the storage device viaan encrypted network and capable of executing machine-readableinstructions to perform program steps, the program steps comprising:retrieving a tie mark file from the database; instantiating aninspection process on the tie mark file to generate an inspectioninformation table and a tie grid having metadata related to a pluralityof ties; editing the tie mark file; and storing the edited tie mark fileto the database. Wherein the program steps further comprise receiving anentry selecting a first tie in the tie grid and generating a graphicemphasizing the selection via the processor. Wherein the program stepsfurther comprise generating an indication if a tie in the tie grid ismarked for replacement. Wherein the program steps further comprisechanging the first tie metadata, via the processor, if a FLIP command isreceived. Wherein the program steps further comprise instantiating animage capture function of the client and storing a captured image in thefirst tie metadata. Wherein the program steps further compriseinstantiating, via the processor, a user input field and storing inputdata in the first tie metadata. Wherein the program steps furthercomprise determining railroad track characteristics and displaying therailroad track characteristics in the tie grid.

In another exemplary embodiment, the present disclosure can include arail tie status processing system, including: a data storage devicehaving a plurality of tie mark files; and a networked computer processoroperably coupled to the storage device via an encrypted network andcapable of executing machine-readable instructions to perform programsteps, the program steps comprising: receiving the location of a clientdevice; indicating the start point and direction of travel on the clientdevice; generating a rail tie status indicator for each of a pluralityof railroad ties in a rail tie file; and receiving input verifying orchanging the status of the rail tie. The system further comprisingdisplaying a graphic showing one or more rail ties for a section trackassociated with the rail tie file. Wherein the graphic can indicate thetie type, the tie number, attributes or characteristics related to therailroad tracks.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary railroad tie management system inaccordance with one or more exemplary embodiments of the presentdisclosure;

FIG. 2 illustrates an exemplary diagram of a railroad tie managementsystem in accordance with one or more exemplary embodiments of thepresent disclosure;

FIG. 3 illustrates railroad tie management system control logic inaccordance with one or more exemplary embodiments of the presentdisclosure;

FIG. 4 illustrates rail tie status processing control logic, inaccordance with one or more exemplary embodiments of the presentdisclosure;

FIG. 5 illustrates railroad tie management and processing system controllogic in accordance with one or more exemplary embodiments of thepresent disclosure;

FIGS. 6A-6B illustrate railroad tie inspection control logic inaccordance with one or more exemplary embodiments of the presentdisclosure;

FIGS. 7A-7B illustrate an exemplary embodiment of a railroad tiemanagement system component in accordance with one or more exemplaryembodiments of the present disclosure;

FIGS. 8A-8C illustrates an exemplary embodiment of a railroad tiemanagement system component, in accordance with one or more exemplaryembodiments of the present disclosure;

FIGS. 9A-9D illustrate a railroad tie management system interface toprovide tie mark files to the client device for download, in accordancewith one or more exemplary embodiments of the present disclosure;

FIGS. 10A-10F illustrate an exemplary embodiment of a railroad tiemanagement system component, in accordance with one or more exemplaryembodiments of the present disclosure; and

FIGS. 11A-11B illustrate an exemplary embodiment of a railroad tiemanagement system component, in accordance with one or more exemplaryembodiments of the present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

The preferred version of the disclosure presented in the followingwritten description and the various features and advantageous detailsthereof, are explained more fully with reference to the non-limitingexamples included in the accompanying drawings and as detailed in thedescription, which follows. Descriptions of well-known components havebeen omitted so to not unnecessarily obscure the principle featuresdescribed herein. The examples used in the following description areintended to facilitate an understanding of the ways in which thedisclosure can be implemented and practiced. Accordingly, these examplesshould not be construed as limiting the scope of the claims.

FIG. 1 illustrates a schematic view of a railroad tie management system100, in accordance with one or more embodiments of the presentdisclosure. The railroad tie management system 100 can included arailroad tie management system server 102 operably coupled to a database104. The server 102 can be operably coupled to one or more clients 108,via a network connection 106. The clients 108 can be a physical device(e.g., mobile phones, computers, or other suitable device), program, orapplications. In another exemplary embodiment, a client 108 can includea mobile device with a mobile application configured to communicate withthe server 102.

The server can be implemented in hardware, software, or a suitablecombination of hardware and software therefor, and may comprise one ormore software systems operating on one or more servers, having one ormore processors, with access to memory. Server(s) can include electronicstorage, one or more processors, and/or other components. Server(s) caninclude communication lines, or ports to enable the exchange ofinformation with a network and/or other computing platforms. Server(s)can also include a plurality of hardware, software, and/or firmwarecomponents operating together to provide the functionality attributedherein to server(s). For example, server(s) can be implemented by acloud of computing platforms operating together as server(s).Additionally, the server can include memory.

Memory can comprise electronic storage that can include non-transitorystorage media that electronically stores information. The electronicstorage media of electronic storage may include one or both of systemstorage that can be provided integrally (i.e., substantiallynon-removable) with server(s) and/or removable storage that can beremovably connectable to server(s) via, for example, a port (e.g., a USBport, a firewire port, etc.) or a drive (e.g., a disk drive, etc.).Electronic storage may include one or more of optically readable storagemedia (e.g., optical disks, etc.), magnetically readable storage media(e.g., magnetic tape, magnetic hard drive, floppy drive, etc.),electrical charge-based storage media (e.g., EEPROM, RAM, etc.),solid-state storage media (e.g., flash drive, etc.), and/or otherelectronically readable storage media. Electronic storage may includeone or more virtual storage resources (e.g., cloud storage, a virtualprivate network, and/or other virtual storage resources). Electronicstorage may store machine-readable instructions, software algorithms,information determined by processor(s), information received fromserver(s), information received from computing platform(s), and/or otherinformation that enables server(s) to function as described herein. Theelectronic storage can also be accessible via a network connection.

Processor(s) may be configured to provide information processingcapabilities in server(s). As such, processor(s) may include one or moreof a digital processor, an analog processor, a digital circuit designedto process information, an analog circuit designed to processinformation, a state machine, and/or other mechanisms for electronicallyprocessing information, such as FPGAs or ASICs. The processor(s) may bea single entity or include a plurality of processing units. Theseprocessing units may be physically located within the same device, orprocessor(s) may represent processing functionality of a plurality ofdevices operating in coordination or software functionality.

The processor(s) can be configured to execute machine-readableinstruction or learning modules by software, hardware, firmware, somecombination of software, hardware, and/or firmware, and/or othermechanisms for configuring processing capabilities on processor(s). Asused herein, the term “machine-readable instruction” may refer to anycomponent or set of components that perform the functionality attributedto the machine-readable instruction component. This can include one ormore physical processors during execution of processor readableinstructions, the processor readable instructions, circuitry, hardware,storage media, or any other components.

The server can be configured with machine-readable instructions havingone or more functional modules. The machine-readable instructions can beimplemented on one or more servers, having one or more processors, withaccess to memory. The machine-readable instructions can be a singlenetworked node, or a machine cluster, which can include a distributedarchitecture of a plurality of networked nodes. The machine-readableinstructions can include control logic for implementing variousfunctionality, as described in more detail below. The machine-readableinstructions can include certain functionality associated with therailroad tie management system 100.

For the railroad tie management system 100, the format for messagestransmitted to and from, for example, the server 102 and clients 108,can include any format, including JavaScript Object Notation (JSON),TCP/IP, XML, HTML, ASCII, SMS, CSV, API, or other suitable format. Eachmessage can consist of a message header, header properties, and amessage body, or be encapsulated and packetized by any suitable formathaving same, including representational state transfer (REST). Theaforementioned system components (e.g., server(s) and client(s)) can becommunicably coupled to each other via the Internet, intranet, or othersuitable network. The message transmission can be encrypted,unencrypted, over a VPN tunnel, or other suitable communication means.The components of the system 100 can be a connected via WAN, LAN, PAN,or other suitable network 106. The network communication between theclients 108 and the sever 100 can be encrypted using PGP, Blowfish,Twofish, AES, 3DES, HTTPS, or other suitable encryption. The system 100can be configured to communicate with the various other systems andmodules disclosed herein using Wi-Fi, Bluetooth, Ethernet, or othersuitable communication protocol. The network communication can occur viaapplication programming interface (API), PCI, PCI-Express, ANSI-X12,Ethernet, Wi-Fi, Bluetooth, or other suitable communication protocol.Additionally, third party databases can be operably connected to thesystem components via the network 106.

FIG. 2 shows a diagram of a railroad tie management system 200 with anumber of subsystems, including, for example, a dashboard system 202, atie audit system 204, a tie mark retrieval system 206, and a settingssystem 208, in accordance with one or more exemplary embodimentsaccording to the present disclosure. In one embodiment, the tie auditsystem 204, tie mark retrieval system 206, and settings system 208 canbe subsystems of the dashboard system 202. In one exemplary embodiment,the railroad tie management system 200 is implemented partly via amobile application on a smart device, wherein aspects of the system areresponsive to user commands and inputs to achieve variable results. Forexample, the railroad tie management system 200 can include a smartphoneexecuting machine-readable instructions comprising an installed mobileapplication that includes the dashboard system 202. Via the dashboard202, the user can communicate with the railroad tie management systemserver 102 and database 104 via the internet 106, as seen in FIG. 1. Inanother exemplary embodiment, the railroad tie management system 200 canbe implemented as an application on a smart device and be in operablecommunication with the server 102 and database 104, and the dashboardsystem 202, tie audit system 204, tie mark retrieval system 206, andsettings system 208 can operate as subsystems to the implementedapplication.

FIG. 3 illustrates a flow chart diagram 300 exemplifying control logicembodying features of a method for railroad tie dashboard generation andmanagement, in accordance with one or more exemplary embodiments of thepresent disclosure. The railroad tie dashboard control logic 300 can beimplemented as an algorithm on a server, a machine learning module, orother suitable system. The railroad tie dashboard control logic 300 canbe achieved with software, hardware, an application programminginterface (API), a network connection, a network transfer protocol,HTML, DHTML, JavaScript, Dojo, Ruby, Rails, other suitable applications,or a suitable combination thereof.

The railroad tie dashboard control logic 300 can leverage the ability ofa computer platform to spawn multiple processes and threads byprocessing data simultaneously. The speed and efficiency of the railroadtie dashboard control logic 300 can be greatly improved by instantiatingmore than one process to generate and manage a railroad tie dashboard.However, one skilled in the art of programming will appreciate that useof a single processing thread may also be utilized and is within thescope of the present disclosure.

The railroad tie dashboard control logic 300 process flow of the presentembodiment begins at step 302, where the control logic 300 can receivean access request from a client. In one exemplary embodiment, the clientcan be a mobile application executed on a mobile smart device, accordingto the present disclosure. The control logic 300 then proceeds to step304.

At step 304, the control logic 300 can generate and render a loginscreen to allow the user to access the system. In one exemplaryembodiment, the client can prompt a user to enter a username andpassword, fingerprint, face image, or other suitable data. The controllogic 300 then proceeds to step 306.

At step 306, the control logic 300 can determine whether a userauthentication is successful. In one exemplary embodiment, the controllogic 300 can initiate the authentication of user credentials, viaauthentication key matching, or other suitable authentication method. Ifthe authentication 306 fails, the client can redisplay the login screen304 and redisplay the login screen 304 until the authentication issuccessful, or the maximum number of attempts is reached. If theauthentication 306 is successful, the client can display a dashboardhaving links to one or more of systems and subsystems, such as, forexample, the dashboard system 202, tie audit system 204, tie markretrieval system 206, and settings system 208. In another exemplaryembodiment, the dashboard system 202 can render and retrieve railroadtie files locally. In another exemplary embodiment, the dashboard system202 can retrieve railroad tie files stored in a remote database or othersuitable location. The dashboard system 202 can also render anindication of the number of ties audited and the number of ties marked.The rendering can be on a client device. In another exemplaryembodiment, the dashboard system 202 can also identify a status ofavailable railroad tie files. For example, the status can include anindication that a file is “in progress” or “completed,” among othersuitable status. In another exemplary embodiment the railroad tie filescan be sorted according to status. The control logic 300 then terminatesor awaits new authentication information and can repeat theaforementioned steps.

FIG. 4 illustrates a flow chart diagram 400 exemplifying control logicembodying features of a method for rail tie status processing, inaccordance with one or more exemplary embodiments of the presentdisclosure. The rail tie status processing control logic 400 can beimplemented as an algorithm on a server, a machine learning module, orother suitable system. The rail tie status processing control logic 400can be achieved with software, hardware, an application programminginterface (API), a network connection, a network transfer protocol,HTML, DHTML, JavaScript, Dojo, Ruby, Rails, other suitable applications,or a suitable combination thereof.

The rail tie status processing control logic 400 can leverage theability of a computer platform to spawn multiple processes and threadsby processing data simultaneously. The speed and efficiency of the railtie status processing control logic 400 can be greatly improved byinstantiating more than one process to process the status of a rail tie.However, one skilled in the art of programming will appreciate that useof a single processing thread may also be utilized and is within thescope of the present disclosure.

The rail tie status processing control logic 400 process flow of thepresent embodiment begins at step 402, where the control logic 400 canaccess one or more railroad tie files. In one exemplary embodiment, thetie files can include a file identifier. The file identifier can be afile name or other unique identifier. In another exemplary embodiment,the file identifier can be related to the railroad track segment,location, or other relevant information. In another exemplary embodimentthe railroad tie files can be accessed on a client device, such as amobile application executed on a mobile smart device, a laptop, asmartwatch, or other suitable device. The control logic 400 thenproceeds to step 404.

At step 404, the control logic 400 can determine a railroad tie filestatus for each tie file. In one exemplary embodiment, the file statuscan indicate whether, how, when, where, and by whom the file has beenused by the control logic 400. In another exemplary embodiment, the filestatus can include “not started,” “in progress,” and “completed,” amongother relevant status. The control logic 400 then proceeds to step 406.

At step 406, the control logic 400 can sort the railroad tie filesaccording to the file status. In one exemplary embodiment, the filestatus can be sorted according to whether, how, when, where, and by whomthe file has been used by. In one exemplary embodiment, the tie markfiles can be sorted by the control logic 400 according to sequentialsearch, bubble search, or quick search algorithms, among others. Thecontrol logic 400 then proceeds to step 408.

At step 408, the control logic 400 can display the file identifiers forthe sorted tie files on a client device. The control logic 400 thenproceeds to step 410.

At step 410, the control logic 400 can generate a file action indicatorto selectively process the tie file. In one exemplary embodiment, thefile action indicator can be a symbol or character displayed proximate afile identifier on the client device. In another exemplary embodiment,the file action indicator can instantiate a process that can upload acompleted type file, open a tie file, or download a tie file, amongother relevant actions. The control logic 400 then proceeds to step 412.

At step 412, the control logic 400 can Receive the location of theclient device. In one exemplary embodiment, a GPS receiver can bedisposed within or operably coupled to the client device. The controllogic 400, can receive the GPS coordinates of the client device, toidentify the location of the client device. In another exemplaryembodiment, the location of the client device can be identified via asymbol on a map displayed on the client device. The control logic 400then proceeds to step 414.

At step 414, the control logic 400 can indicate a start point and adirection of travel on the client device. In one exemplary embodiment,the control logic 400 can generate a notification or indication adirection of travel to the start point. The start point and thedirection of travel can be indicated as symbols on a map, audibleinstructions played via speakers on the client device, textualdirections (e.g., latitude and longitude), or other suitable means. Thecontrol logic 400 then proceeds to step 416.

At step 416, the control logic 400 can display a graphic showing one ormore rail ties for a section of track associated with the tie file. Inone exemplary embodiment, the graphic can indicate the tie type, the tienumber, attributes or characteristics related to the railroad tracks, orother relevant information. The control logic 400 then proceeds to step418.

At step 418, the control logic 400 can generate a rail tie status usingthe tie file. In one exemplary embodiment, the rail tie status canindicate the nature or condition of the rail tie. For example, the railtie status can indicate whether a tie is worn, needs to be replace oracceptable. In another exemplary embodiment the control logic 400 canretrieve the status from the tie file and populate the status of therail tie via automated scanning for verification. In another exemplaryembodiment, the tie file can be an XML file having a plurality of fieldsdescribing various characteristics of a rail tie, a section or railroad,or other relevant subject matter. The control logic 400 then proceeds tostep 420.

At step 420, the control logic 400 can generate a tie status indicatorfor each rail tie. In one exemplary embodiment, a symbol or charactercan be generated by the control logic by correlating the tie status witha library of status indicators to display the relevant indicator at ornear each rail tie in the client device display. The control logic 400then proceeds to step 422.

At step 422, the control logic 400 can receive input verifying orchanging the status of each rail tie in the tie file. In one exemplaryembodiment, the control logic can generate and display one or morestatus for a rail tie such that a user can select an appropriate status.In another exemplary embodiment, the control logic 400 can generatecontrols for incrementing or decrementing through each rail tie. Oncethe desired rail tie is selected the control logic 400 can receive inputfrom a user regarding the status of the rail tie, either verifying or“flipping” the status of the selected rail tie. The control logic 400then terminates or awaits input to repeat the aforementioned steps.

FIG. 5 illustrates a flow chart diagram 500 exemplifying control logicembodying features of a method for railroad tie file management andprocessing, in accordance with one or more exemplary embodiments of thepresent disclosure. The railroad tie file control logic 500 can beimplemented as an algorithm on a server, a machine learning module, orother suitable system. The railroad tie file control logic 500 can beachieved with software, hardware, an application programming interface(API), a network connection, a network transfer protocol, HTML, DHTML,JavaScript, Dojo, Ruby, Rails, other suitable applications, or asuitable combination thereof.

The railroad tie file control logic 500 process flow of the presentembodiment begins at step 502, where the control logic 500 caninstantiate of the dashboard system 502. In one exemplary embodiment,the client can be a mobile application executed on a mobile smartdevice, according to the present disclosure. The control logic 500 thenproceeds to step 504. At step 504, the control logic 500 can determinewhether tie mark files are available locally (e.g., stored on the clientdevice). In another exemplary embodiment, the control logic 500 candetermine whether the tie mark files can be accessed remotely (e.g., ona network-attached storage, server, database, or other suitable remotelocation). If a desired tie mark file is available locally, the controllogic 500 proceeds to step 514. If a desired tie mark file is notavailable locally, the control logic 500 proceeds to step 506.

At step 506, the control logic 500 can instantiate the tie markretrieval system 506. In one exemplary embodiment, the control logic 500can be instantiated to facilitate the serving of tie mark files from therailroad tie management system server or database to the client. Thecontrol logic 500 then proceeds to step 508.

At step 508, the control logic 500 can determine whether anauthentication is successful. The authentication can be for a user, adevice, or other suitable entity. In one exemplary embodiment, thecontrol logic 500 can initiate the authentication of user credentials,via authentication key matching, or other suitable authenticationmethod. If the authentication 508 fails, the control logic 500 proceedsto step 502. If the authentication 508 is successful, the control logic500 proceeds to step 510.

At step 510, the control logic 500 can generate a user prompt to verifythe user's consent to permissions requested by the server 510. In oneexemplary embodiment, requested permissions can include access to clientresources, such as microphone, network, and other suitable resources, aswell as client location and data. The control logic 500 then proceeds tostep 512.

At step 512, the control logic 500 can serve the requested tie markfiles to the client 512. In one exemplary embodiment, the tie mark filescan be transmitted via an encrypted network. The network communicationbetween the client and the server can be encrypted using PGP, Blowfish,Twofish, AES, 3DES, HTTPS, or other suitable encryption. The controllogic 500 then proceeds to step 514.

At step 514, the control logic 500 can sort the tie mark files intopredetermined categories. In one exemplary embodiment, the tie markfiles include metadata related to various characteristics of the file,including, timestamp, status, inspector, locations, and other suitablemetadata. The metadata can then be grouped according to like categories,which can be predetermined or generated by the device. In anotherexemplary embodiment, the predetermined categories can include “NOTSTARTED,” referring to tie mark files that have been downloaded from theserver but not yet interacted with on the client device; “IN PROGRESS,”referring to tie mark files that have been interacted with on the clientdevice but not yet marked as completed; “COMPLETED,” referring to tiemark files that have been marked as completed; or “RECENTLY WORKED,”referring to the files that have been most recently downloaded,accessed, viewed, or otherwise interacted with. It will be appreciatedthat a myriad of other categories could be used, such by geographicallocation, number of ties remaining to be inspected, priority, etc. Thecontrol logic 500 then proceeds to step 516.

At step 516, the control logic 500 can extrapolate various data relatedto the railroad tie file. In one exemplary embodiment, a selection of aparticular tie mark file can be received (e.g., file name, timestamp,locations, etc.), and the system can generate a display of the tie markfile details at step 518. In one exemplary embodiment, the control logic500 can generate and display a graphic showing one or more railroadties. In another exemplary embodiment, the graphic can be processed bythe control logic 500 to create one or more indicators to characterizeeach railroad tie, using the railroad tie information from the railroadtie file. An entry of milepost designation can then be received at step520 (which, in one embodiment, communicates to the system at whichmilepost the user will be inspecting ties), followed by a directionentry at step 522, to indicate the direction of the inspection. Inanother exemplary embodiment, the direction entry can be either“INCREASING” or “DECREASING,” corresponding to west and east,respectively. The control logic 500 then awaits user input and caneither proceed to step 524 if an “inspect” command is received, step 540if a “settings” command is received, or step 542 if an “audit” commandis received.

At step 524, the control logic 500 can receive an “inspect” command. Inone exemplary embodiment, the inspect command can generate a graphicshowing one or more rail ties for a section of track associated with thetie file. In another exemplary embodiment, the inspect command candisplay a rail tie status indicating the nature or condition of eachrail tie in the tie file. In another exemplary embodiment, tie statusindicator can be generated for each rail tie. In another exemplaryembodiment, a symbol or character can be generated by the control logicby correlating the tie status with a library of status indicators todisplay the relevant indicator at or near each rail tie on the clientdevice display. The control logic 500 then proceeds to step 526.

At step 526, an inspection process can be instantiated to inspect thedata of a tie mark file. In one exemplary embodiment, the graphic canindicate the tie type, the tie number, attributes or characteristicsrelated to the railroad tracks, or other relevant information. Inanother exemplary embodiment, the rail tie status can indicate thenature or condition of the rail tie. In another exemplary embodiment,the control logic can generate and display one or more status for a railtie such that a user can select an appropriate status. In anotherexemplary embodiment, the control logic 500 can generate controls forincrementing or decrementing through each rail tie. Once the desiredrail tie is selected the control logic 400 can receive input from a userindicating the status of the rail tie. The control logic 500 thenproceeds to step 528.

At step 528, when the inspection is complete, the control logic 500 canreceive and confirm a save command. In one exemplary embodiment, theprogress of an inspection can be stored locally on the client device.The control logic 500 then proceeds to step 530.

At step 528, the control logic 500 can receive and confirm a “markcomplete” command that terminates the inspection process and writes anyand all metadata related to the inspection of rail ties captured by thecontrol logic 500 to the tie mark file. In one exemplary embodiment, thetie file can be marked as completed, ultimately causing the tie markfile to be sorted, categorized, and displayed accordingly on thedashboard system. The control logic 500 then terminates or awaits inputto repeat the aforementioned steps.

At step 532, the control logic 500 can receive an “upload” command toupload the completed tie file to a remote location. In one exemplaryembodiment, once a locally available tie mark file is marked ascomplete, an upload command can be received by the control logic 500 toinitiate transfer of the completed file to a remote location, such as aserver, network storage, or other relevant location. The control logic500 then proceeds to step 534.

At step 534, the control logic 500 can authenticate a user orcommunicate with another system that can authenticate the user. In oneexemplary embodiment, the control logic 500 can initiate theauthentication of user credentials, via authentication key matching, orother suitable authentication method. In another exemplary embodiment,in order for a user to upload a tie file, the user must beauthenticated. The control logic then proceeds to step 536.

At step 536, the control logic 500 can determine whether a userauthentication is successful. If the authentication 534 fails, thecontrol logic 500 can redisplay a login screen on the client devicedisplay and redisplay the login screen until the authentication issuccessful, or the maximum number of attempts is reached. If theauthentication is confirmed, the control logic 500 then proceeds to step538.

At step 538, the control logic 500 can upload one or more updated tiemark files from the client device to the remote location, via anencrypted or unencrypted network connection. The control logic 500 thenterminates or awaits new input and can repeat the aforementioned steps.

FIGS. 6A-6B illustrate a flow chart diagram 600 (beginning on FIG. 6Aand continuing on FIG. 6B) exemplifying control logic embodying featuresof a method for railroad tie inspection, in accordance with one or moreexemplary embodiments of the present disclosure. The railroad tieinspection control logic 600 can be implemented as an algorithm on aserver, a machine learning module, or other suitable system. Therailroad tie inspection control logic 600 can be achieved with software,hardware, an application programming interface (API), a networkconnection, a network transfer protocol, HTML, DHTML, JavaScript, Dojo,Ruby, Rails, other suitable applications, or a suitable combinationthereof.

Referring to FIG. 6A, the railroad tie inspection control logic 600process flow of the present embodiment can begin at step 602, where thecontrol logic 500 can instantiate an inspection process. Uponinstantiation of the inspection process 602, an inspection informationtable can be generated at step 608. As discussed with respect to FIG. 5,the user can select either an INCREASING or DECREASING direction whenselecting a tie mark file for inspecting and prior to inspection processinstantiation. At step 604, in one exemplary embodiment, if theINCREASING direction is selected, the control logic 600 can generate atie grid with ties sorted in ascending order by tie number. At step 606,if the DECREASING direction is selected, the control logic 600 cangenerate a tie grid with ties sorted in descending order by tie number.

At step 610, the generated tie grid can be responsive to a number ofuser inputs. For example, a find tie command can be received, which canprompt the user to enter a desired tie number. If the find tie commandis received, the control logic proceeds to step 612. If the find tiecommand is not received, the control logic proceeds to step 618.

At step 612, the tie number entry can be received by the control logic600. At step 614, a find distance command can be received by the controllogic 600. At step 616, the control logic 600 can calculate and displaya physical distance between the tie specified and the client device. Inone exemplary embodiment, such distance calculation can utilize, forexample, a GPS receiver operably coupled to a client device, such as,for example, a mobile smart device (permission for which can be granted,for example, when permissions are requested such as in FIG. 5 at 510).At step 620, a go to tie command can be received to navigate a user tothe specified tie in the tie grid at step 622.

At step 618, the control logic can receive navigation entries tonavigate to a specific tie in the tie grid. In another exemplaryembodiment, instead of using control logic 600 generated commands, auser can use manual entries (e.g., scrolling, arrow keys, or any othersuitable user input interface) to manually navigate to a specific tie inthe tie grid.

At step 624, once a desired tie is navigated to, a selection entry of aspecific tie can be received and emphasized. In one exemplaryembodiment, the control logic 600 can display a selected tie on theclient device, such that the selected tie can be highlighted, colored,bolded, or otherwise made to stand out from non-selected ties in the tiegrid.

At step 626, a tie can be marked for replacement. In one exemplaryembodiment, such designation is already programmed into the tie markfile. The control logic 600 can parse the attributes for a particulartie from the tie file and render the tie on the client device pursuantto such attributes.

At step 628, the control logic can generate an indication to inform theuser of the attributes for the tie and the tie is so marked. In oneexemplary embodiment, the indication can be visual (color), tactile(vibration), audible (sound), etc.), or other relevant user indication.

If a tie is not marked for replacement at step 626, the control logic600 can determine that no action should be taken at step 644. In oneexemplary embodiment, the user can tag the tie with metadata indicatingthat no action should be taken, via the control logic 600. At step 630,a FLIP command can also be received by the control logic 600. The FLIPcommand can be selected by the user via the client device.

At step 632, the designation (status) of the tie can be switched betweenaction and no action, and the control logic can display such change tothe user. In another exemplary embodiment, a tie marked for replacementwill no longer be marked for replacement, and a tie not so marked willbecome so marked.

At step 634, a COMMENT command can be received by the control logic 600.In one exemplary embodiment, the tie grid can be navigable via userinput commands such as PREVIOUS and NEXT, wherein the commands navigatethe grid and select the tie immediately adjacent to the currentlyselected tie in the indicated direction. In another exemplaryembodiment, this functionality can be coupled with a controller, such asa Bluetooth wireless controller.

At step 636, the control logic can generate a user input field that canallow a user to input data about the specific tie. In one exemplaryembodiment, the control logic 600 can tag the tie in the file withmetadata indicating the user-generated or selected tie data.

At step 638, it is determined whether the control logic 600 received aCAMERA command. In one exemplary embodiment, the client device caninclude a camera. If no camera command is received, the control logiccontinues to step 644. If a CAMERA command is received, the controllogic continues to step 640.

At step 640, the control logic can instantiate a client device camerafunction (such permissions attainable, for example, at step 510 of FIG.5). In one exemplary embodiment, the control logic 600 can capture oneor more images via the client device camera. At step 642, the controllogic 600 can associate a captured image with a selected tie. In oneexemplary embodiment, the control logic 600 can store the images asmetadata associated with a particular rail tie in or appended to the tiefile.

Referring to FIG. 6B after instantiation of the inspection process atstep 602. As above, at step 608, an inspection information table can begenerated that can include a number of displays and fields. At step 648,the control logic 600 can display the currently selected tie in the TIESfield using the data contained in the information table. At step 648,the control logic 600 can display the ties replaced in the REPLACE field650. The control logic 600 can also display the number of tiespreviously marked for replacement that have been removed from suchcategory in the REMOVED field; the ADDED field can indicate how manyties have been added to the total ties-marked-for-replacement count; theBANKER field can display the difference between the REMOVED and ADDEDfields as an indication of tie allotment to those categories; and theOVERALL MARKED field can indicate how many ties in the selected tie markfile are marked for replacement.

The control logic 600 can automatically update fields in response touser interaction with the tie grid. The control logic can includeregisters that can store incrementation and decrementation countervalues. At step 652, if a tie that was previously marked for replacementis “flipped,” at step 654, the REMOVED field counter can be incremented.In one exemplary embodiment, flipping the field can indicate that amarked tie has been removed. At step 656, this increment can then causean increment in the BANKER field counter (indicating that the user hasan “extra” tie, because the previously-marked tie is no longer markedfor replacement, meaning a new tie will not be needed, so such new tieis available for use in the “bank”), or alternatively, the incrementscan happen simultaneously.

At step 660, if a tie that was not previously marked for replacement is“flipped” to become marked for replacement, the ADDED field can beincremented by the control logic 600 accordingly. This increment canthen cause the BANKER field to be decremented by the control logic atstep 664, indicating that a new tie is “withdraw” from the “bank” toreplace the tie now marked for replacement. The increments anddecrements in the inspection information table can likewise affect theOVERALL MARKED field counter, causing decrements at step 658 andincrements at step 666 as appropriate. At step 668, the control logiccan take no action. The control logic 600 then terminates or awaits newinput and can repeat the aforementioned steps.

FIGS. 7A and 7B illustrate a railroad tie management system component,in accordance with one or more exemplary embodiments. In one exemplaryembodiment, a mobile application on a client device can request toconnect with the railroad tie management system server and displays adashboard. Referring to FIG. 7A, Authentication is required via a loginscreen 700 where the user can input a user identification 702 andpassword 704. If authentication is successful, the mobile applicationcan instantiate a dashboard system 706. For example, sections of trackcan be organized into files, with the files listing the tie status andcorresponding metadata. These track sections can vary in length basedupon the number of identified issues in a particular section of track,the equipment available, the location accessibility, and other relevantparameters. In one exemplary embodiment, the client device has tie markfiles available locally, enabling the dashboard system 706 to sort thetie mark files for increased accessibility. The tie mark files can besorted according to sequential search, bubble search, or quick searchalgorithms, among others.

In one exemplary embodiment, a tie mark file's metadata can indicate thestatus of the inspection of a particular section of track. In anotherexemplary embodiment, the status can be identified as IN PROGRESS 708,COMPLETED 710, NEW, or other relevant indication. In another embodiment,the dashboard system 706 can receive commands to instantiate a number ofsubsystems via navigation links. Such links can include links: DASHBOARD712, TIE AUDIT 714, TIE MARK 716, SETTINGS 718, among other links. Inanother exemplary embodiment, the number of ties marked or audited canbe displayed by the dashboard system 706 on the client device.

FIGS. 8A, 8B, and 8C illustrate a railroad tie management systemcomponent, in accordance with one or more exemplary embodiments. The TIEMARK navigation link 716 (depicted in FIGS. 7A and 7B) can instantiate,for example, a tie mark retrieval system 800. In this exemplaryembodiment, the tie mark retrieval system 800 can perform as a subsystemof the dashboard system 706, wherein the available local files (e.g.810) remain sorted into multiple categories 804, 806, 808. This tie markretrieval system subsystem 800 can generate a file retrieval request(for example, via the “+” user input link in the top right corner) thatcan be transmitted to the railroad tie management system server. Theserver can require authentication, such as via a login screen 812, andsubsequently request permissions from the user 814 to allow the server(and/or the mobile application in operable communication with theserver) to control certain aspects of the client device. Once theauthentication is completed and needed permissions are granted, theserver can provide tie mark files to the client device for download, asseen in FIGS. 9A-9D.

In one exemplary embodiment, the tie mark files can first be organizedby subdivision (i.e. HASTINGS or ST CROIX) as seen in 900. Afterreceiving a subdivision selection, the client can be served ranges oftie mark files organized by, for example, milepost range (designated by,for example, —MP—173.0-202.0, indicating that the titled tie mark fileincludes ties from milepost 173 to milepost 202 in that specificsubdivision), as seen in 902. Multiple other fields can also beassociated with the tie mark file ranges, such as plan number, trackcode, and line segment. A DOWNLOAD or DOWNLOAD ALL command can then bereceived to enable the client to retrieve copies of the selected tiemark files from the server. Once the tie mark files are availablelocally, they can be sorted accordingly as seen in 904. A given tie markfile can then be selected, prompting the generation of tie mark filedetails as seen in 906. Such details can include the division,subdivision, line segment, track type, milepost range, the date of lastinspection, the status of the tie mark file, and the milepost direction.In one exemplary embodiment, the MILEPOST DIRECTION field can be toggledby the user to select either an INCREASING or a DECREASING direction908. Once this is completed, an inspection process can be instantiatedvia, for example, the INSPECT command (for example, in the top rightcorner in FIG. 9D).

FIGS. 10A-10F illustrate a railroad tie management system component, inaccordance with one or more exemplary embodiments. In one exemplaryembodiment, when an inspection process is instantiated with a tie markfile, an inspection information table 1000 and a tie grid 1018 aregenerated. The inspection information table can include a number offields, such as TIES 1002, REPLACE 1004, ADDED 1006, REMOVED 1008,MILEPOST 1010, OVERALL MARKED 1012, BANKER 1014, and AURORA# 1016(corresponding to an inspection previously performed by, for example,Aurora® scanning technology, which data can be, in one embodiment,previously incorporated into the tie mark file). The inspectioninformation table can be responsive to interaction with the tie grid inaccordance with principles of the present disclosure. The tie grid 1018can include a number of fields, such as: TIE TYPE 1020, corresponding tothe type of tie (i.e. wood, concrete, metal, composite, etc.); INT 1022,referring to the internal density score of the tie as determined by, forexample, an Aurora® scanner; TIE NO 1024, corresponding to the tieidentification number; CRVCAT 1026, referring to the curve category ofthe tie; CMB 1028, corresponding to the combination of the INT score andthe EXT score; and EXT 1030, corresponding to the external score of thetie (i.e. the score determined by examining the surface of the tie). Inan exemplary embodiment, TIE TYPE can display WT (for wood tie), CT(concrete tie), X (crossing tie), or T (turnout tie). In anotherexemplary embodiment, CRVCAT can display T (tangent curve), L (lightcurve), M (moderate curve), or S (severe curve). In another exemplaryembodiment, the INT, EXT, and CMB scores are displayed as decimalnumerals from 1.0-4.0.

In one exemplary embodiment, tie scores (i.e. INT, EXT, and CMB) canrange from 1.0-4.0 as determined via, for example, an Aurora® scanner,in accordance with the following chart:

TIE GRADE CLASSIFICATION 3.5-4.0 2.7--3.4 1.5-2.6 1.0-1.4 FailedMaintenance Marginal Good CONDITION (BLACK) (RED) (YELLOW) (GREEN)Broken Broken through - Broken through - Not broken through No Breaksseparated Not separated Split or To the extent Will not hold Tie holdsspikes, some Slight weather Otherwise the crossties spikes or railsplits deep enough to splits but integrity Impaired will allowfasteners. allow water into tie. Tie not compromised ballast to workLoose spikes in can be plugged and re- through, or will curves greaterspiked if in tangent or not hold spikes than 2 degrees. curves 2 degreesand or rail fasteners less. Deteriorated So that the tie So that the tieLess than ¼ inch of No plate plate or base of plate or base of lateralplate or rail movement or cut rail can move rail can move movement andno sign of laterally more laterally more deterioration than ½ inch than¼ inch but relative to the less than ½ inch crosstie relative to thecrosstie Plate Cut More than 40% More than 1 Greater than ¼ inch, up ¼inch plate cut of the ties' inch but less to 1 inch in depth or less.thickness than 40% of the ties' thickness Wheel Cut More than 2 ½ inchto 2 inches deep ½ inch or less inches deep not broken through the withno structural within 12 tie damage to tie inches of the base of theload-bearing area, not broken through the tie. Rotted or SubstantialSome rot over tie and on None Hollow amount of ends. Not hollow underwood decayed plate area. or missing. Hollow under plate area. ExpectedLess than 20 years 20 years or Remaining greater Life

In one exemplary embodiment, the tie grid 1018 can be color-coded inaccordance with the above chart (i.e. ties with a CMB of 3.5-4.0 arehighlighted black, 2.7-3.4 are highlighted red, 1.5-2.6 are highlightedyellow, and 1.0-1.4 are highlighted green). Additionally, ungraded ties(such as ties that cannot be scanned by, for example, an Aurora®scanner, i.e. ballast covered ties, ties obscured by heavy vegetation ormud spots, ties on turnouts and road crossings, ties on inner guard raillocations, etc.) can be highlighted blue and have an INT, EXT, and CMBof −1.0 to indicate that they are ungraded. In another exemplaryembodiment, a user command can be received to enter a manual INT, EXT,and/or CMB for an ungraded tie.

In one exemplary embodiment, the tie grid 1018 can be navigatedmanually, e.g., a user can “scroll” through the grid to locate thedesired tie. In another exemplary embodiment, a FIND TIE command 1032can be received which subsequently prompts a user to enter the tienumber 1034 that the user would like to navigate to. After entering thetie number 1034, the FIND DISTANCE command can also be received,calculating and displaying the physical distance between the clientdevice and the specified tie, as well as the latitude and longitude ofthe specified tie. After the tie number entry 1034 is received, the GOTO TIE command 1038 can be received, which automatically navigates theuser to the specified tie in the tie grid. While navigating the tiegrid, specific ties can be selected, and such selection can beemphasized, for example, via highlighting as seen in FIG. 10D. In oneembodiment, ties marked for replacement can have a visual indicator 1042disposed in the TIE TYPE column (e.g. here, a square 1042). If a FLIPcommand 1040 is received for a tie marked for replacement, the tie willbe marked accordingly; for example, a red X can appear in the black box1042 indicating that the tie is no longer marked for replacement. Inanother exemplary embodiment, if a FLIP command 1040 is received for aselected tie that was not marked for replacement, a visual indicator1044 can be disposed in the TIE TYPE column (e.g. here, a circle 1044).

In another exemplary embodiment, a CAMERA command 1048 can be receivedthat instantiates an image capture function on the client device inaccordance with the principles of the present disclosure. In anotherexemplary embodiment, a COMMENT command 1046 can be received that causesthe generation of a user input field 1050 in accordance with theprinciples of the present disclosure. In another exemplary embodiment, aMARK COMPLETED command 1052 can be received, updating the metadata ofthe tie mark file to indicate that the file can be sorted into theCOMPLETED category in the dashboard system.

Referring to FIGS. 11A and 11B, 1100 displays the dashboard systemrunning a tie mark subsystem, wherein a tie mark file is categorized asCOMPLETED. The system can determine that, because the file is COMPLETED,the tie mark file can be retrieved by the server. To instantiate thisprocess, an upload command 1102 can be received, followed by aconfirmation 1104. The uploaded tie mark file can then be accessible byother components of the railroad tie management system, such as by otherclients.

The present disclosure achieves at least the following advantages:

-   -   1. improves organization and accessibility of tie inspections        and tie replacements via tie grids and other technological        improvements;    -   2. increases efficiency of tie inspections and tie inspectors        via improved systems that can add and modify metadata tags        related to tie files;    -   3. provides a platform for facilitating tie inspections and tie        marking; and    -   4. provides centralized and accessible data sets for ties        throughout railroad infrastructure, enabling faster and        more-informed decision making.

Persons skilled in the art will readily understand that these advantages(as well as the advantages indicated in the summary) and objectives ofthis system would not be possible without the particular combination ofcomputer hardware and other structural components and mechanismsassembled in this inventive system and described herein. It will befurther understood that a variety of programming tools, known to personsskilled in the art, are available for implementing the control of thefeatures and operations described in the foregoing material. Moreover,the particular choice of programming tool(s) may be governed by thespecific objectives and constraints placed on the implementation planselected for realizing the concepts set forth herein and in the appendedclaims.

The description in this patent document should not be read as implyingthat any particular element, step, or function can be an essential orcritical element that must be included in the claim scope. Also, none ofthe claims can be intended to invoke 35 U.S.C. § 112(f) with respect toany of the appended claims or claim elements unless the exact words“means for” or “step for” are explicitly used in the particular claim,followed by a participle phrase identifying a function. Use of termssuch as (but not limited to) “mechanism,” “module,” “device,” “unit,”“component,” “element,” “member,” “apparatus,” “machine,” “system,”“processor,” “processing device,” or “controller” within a claim can beunderstood and intended to refer to structures known to those skilled inthe relevant art, as further modified or enhanced by the features of theclaims themselves, and can be not intended to invoke 35 U.S.C. § 112(f).

The disclosure may be embodied in other specific forms without departingfrom the spirit or essential characteristics thereof. For example, eachof the new structures described herein, may be modified to suitparticular local variations or requirements while retaining their basicconfigurations or structural relationships with each other or whileperforming the same or similar functions described herein. The presentembodiments are therefore to be considered in all respects asillustrative and not restrictive. Accordingly, the scope of theinventions can be established by the appended claims rather than by theforegoing description. All changes which come within the meaning andrange of equivalency of the claims are therefore intended to be embracedtherein. Further, the individual elements of the claims are notwell-understood, routine, or conventional. Instead, the claims aredirected to the unconventional inventive concept described in thespecification.

What is claimed is:
 1. A rail tie processing system, comprising: a datastorage device comprising a first database with a plurality of tie markfiles; and a networked computer processor operably coupled to thestorage device via an encrypted network and capable of executingmachine-readable instructions to perform program steps, the programsteps comprising: accessing one or more railroad tie files from memory,each railroad tie file having a file identifier; determining a railroadtie file status for each tie file; sorting the railroad tie filesaccording to the file status; displaying the file identifiers for thesorted railroad tie files on a client device; generating a file actionindicator to selectively process a selected railroad tie file; receivingthe location of a client device; indicating a start point and adirection of travel on the client device based on the selected railroadtie file; and displaying a graphic showing one or more rail ties for asection of track associated with the tie file.
 2. The system of claim 1,wherein the program steps further comprise the step of generating a railtie status for the one or more rail ties based on the selected railroadtie file.
 3. The system of claim 1, wherein the program steps furthercomprise the step of generating a tie status indicator for each rail tiein the selected railroad tie file.
 4. The system of claim 1, wherein theprogram steps further comprise the step of receiving input verifying orchanging the status of a selected rail tie.
 5. The system claim 3,wherein the program steps further comprise the step of identifying oneor more ties for a predetermine section of a railroad track.
 6. Thesystem of claim 1, wherein the program steps further comprise the stepof determining railroad track characteristics and displaying therailroad track characteristics on the client device.
 7. The system ofclaim 1, wherein the program steps further comprise the step ofreceiving an entry selecting a first rail tie and retrieving metadataassociated with the first rail tie via the processor.
 8. The system ofclaim 7, wherein the program steps further comprise the step ofgenerating an indication if the first rail tie is marked forreplacement.
 9. The system of claim 7, wherein the program steps furthercomprise the step of instantiating an image capture function of theclient and storing a captured image in metadata associated with thefirst rail tie.
 10. The system of claim 7, wherein the program stepsfurther comprise the step of instantiating, via the processor, a userinput field and storing input data in the first tie metadata.
 11. Amethod of processing rail ties in a railroad system, the methodcomprising the steps of: accessing one or more railroad tie files frommemory, each railroad tie file having a file identifier; determining arailroad tie file status for each tie file; sorting the railroad tiefiles according to the file status; displaying the file identifiers forthe sorted railroad tie files on a client device; generating a fileaction indicator to selectively process a selected railroad tie file;receiving the location of a client device; indicating a start point anda direction of travel on the client device based on the selectedrailroad tie file; and displaying a graphic showing one or more railties for a section of track associated with the tie file.
 12. The methodof claim 11, further comprising the step of generating a rail tie statusfor the one or more rail ties based on the selected railroad tie file.13. The method of claim 11, further comprising the step of generating atie status indicator for each rail tie in the selected railroad tiefile.
 14. The method of claim 11, further comprising the step ofreceiving input verifying or changing the status of a selected rail tie.15. The method claim 13, further comprising the step of identifying oneor more ties for a predetermine section of a railroad track.
 16. Themethod of claim 11, further comprising the step of determining railroadtrack characteristics and displaying the railroad track characteristicson the client device.
 17. The method of claim 11, further comprising thestep of receiving an entry selecting a first rail tie and retrievingmetadata associated with the first rail tie via the processor.
 18. Themethod of claim 17, further comprising the step of generating anindication if the first rail tie is marked for replacement.
 19. Themethod of claim 17, further comprising the step of instantiating animage capture function of the client and storing a captured image inmetadata associated with the first rail tie.
 20. The method of claim 17,further comprising the step of instantiating, via the processor, a userinput field and storing input data in the first tie metadata.